Vehicle system passive notification using remote device

ABSTRACT

A method of vehicle monitoring includes monitoring one or more vehicle safety systems while a vehicle is in operation to detect an unsafe condition. The method also includes sending an alert to a handheld device if an unsafe condition is detected.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 12/571,517 filed Oct. 1, 2009, now U.S. Pat. No. 8,558,690, the disclosure of which is hereby incorporated in its entirety by reference herein.

TECHNICAL FIELD

The illustrative embodiments generally relate to vehicle system passive notification using a remote device.

BACKGROUND

Cellular phone and PDA displays are growing increasingly capable of displaying an ever more complex variety of information. Color, touch-sensitive displays can present a user with graphic interfaces, detailed figures, and a variety of other interactive information.

Additionally, there is an increasing need in society to have information access on-demand. In a world of GOOGLE, YAHOO! and WIKIPEDIA, users are growing used to having any and all desired information at their fingertips.

This information, while useful in many areas, is also often static information. That is, it is fixed, factual information. Integration, however, of dynamic “facts” has slowly begun.

Also, it is now possible to have updates, such as an update indicating when a bill is due, sent to a cellular phone as, for example, a text message.

SUMMARY

In a first illustrative embodiment, a method for monitoring a vehicle sensor includes activating one or more monitoring systems and monitoring the one or more activated monitoring systems.

The exemplary method further includes checking a power source providing power to the one or more monitoring systems to determine if the power source is below a certain threshold. The method also includes sending a low power alert to a user on a remote device if the power source determined to be below the threshold, and ceasing monitoring of the one or more systems being monitored if the power source is below the threshold.

Further, the method includes detecting a change in the state of the one or more systems being monitored and sending an alert to the user on the remote device if at least one of the one or more monitoring systems have changed state to a state in which an alert is to be sent.

In a second illustrative embodiment, a method of vehicle monitoring includes monitoring one or more vehicle safety systems while a vehicle is in operation to detect an unsafe condition. The method also includes sending an alert to a handheld device if an unsafe condition is detected.

In a third illustrative embodiment, a method of vehicle monitoring includes determining if a specific driver class is present in a vehicle. This method further includes determining one or more class specific safety systems to monitor based at least in part on a determined driver class. Also, this method includes monitoring the one or more class specific safety systems while a vehicle is in operation to detect an unsafe condition and sending an alert to a handheld device if an unsafe condition is detected.

In a fourth illustrative embodiment, a method of monitoring vehicle systems includes determining if a vehicle system to be monitored is in an alert state and determining if a vehicle is occupied. Based at least in part on the vehicle system alert state determination and whether the vehicle is determined to be occupied, the method may send a vehicle system alert based at least in part on a determined alert state to a user's wireless device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an illustrative example of a communication system through which a nomadic device can communicate with a vehicle;

FIGS. 2 a-d show illustrative examples of vehicle-based communication modules that provide communication to a remote network;

FIG. 3 shows an illustrative example of communication between a remote wireless device and a vehicle based wireless device;

FIG. 4 shows one illustrative embodiment for passively monitoring a vehicle system;

FIG. 5 shows a further illustrative embodiment of a passive monitoring strategy;

FIG. 6 a shows an illustrative example of monitoring a trailer connection;

FIG. 6 b shows a second example of monitoring a weather sensor;

FIG. 7 shows an illustrative example of a notification strategy;

FIGS. 8 a-8 b show illustrative a parking brake monitor systems;

FIG. 9 shows an example of a safety alert monitoring and transmission system; and

FIG. 10 shows an illustrative example of providing monitoring conditions for a specific driver or set of drivers.

DETAILED DESCRIPTION

As required, detailed embodiments of the present invention are disclosed herein; however, it is to be understood that the disclosed embodiments are merely exemplary of the invention that may be embodied in various and alternative forms. The figures are not necessarily to scale; some features may be exaggerated or minimized to show details of particular components. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a representative basis for teaching one skilled in the art to variously employ the present invention.

Detailed embodiments of the present invention are disclosed herein. However, it is to be understood that the disclosed embodiments are merely exemplary of an invention that may be embodied in various and alternative forms. Therefore, specific functional details disclosed herein are not to be interpreted as limiting, but merely as a representative basis for the claims and/or as a representative basis for teaching one skilled in the art to variously employ the present invention.

FIG. 1 shows an illustrative example of a communication system through which a nomadic device can communicate with a vehicle 121. In this illustrative embodiment, a nomadic device (e.g., without limitation, a cellular phone) 103 is used to send a communication through a cellular network 107. This communication is relayed through a network 111 (e.g., without limitation, the cellular network, the internet, etc.) to a centralized system 101. A system similar to the system shown in FIG. 1 is available from CRAYON INTERFACE, INC.

In this illustrative embodiment, the centralized system is a server system that includes processing capability for incoming nomadic device signals designated to interact with a remote vehicle 121.

For example, the server(s) 101 may include an automated call server and/or web host. Further, the server(s) 101 may route an incoming signal from a nomadic device (ND) 103 to the appropriate remote vehicle. Data sent in this fashion may be sent using data-over-voice, a data-plan, or in any other suitable format.

Data can also be sent to the remote vehicle 121 through the server(s) 101 using a personal computer 105. In this case, the data is likely, although not necessarily, sent over the internet 109.

Once the server(s) 101 receive the incoming data request from the remote source 103, 105, the message is processed and/or relayed to a vehicle 121. The vehicle may be identified by a header associated with one or more incoming data packets, or may be identifiable based on a database lookup, for example.

The relay to the vehicle 121 is sent out from the server(s) 101 through a network (e.g., without limitation, a cellular network 113, the internet, etc.) and passed through a cellular network 115 to the vehicle 121. In one embodiment, the relay may additionally be passed through a broadband network 114 (e.g., 802.11g or WiMax). A remote communication module 200 in the vehicle 121 receives the signal sent from the server(s) 101 and processes it or relays it to an appropriate processing system within the vehicle 121.

In at least one illustrative embodiment, the vehicle 121 is also outfitted with a communication transceiver, such as, but not limited to, a BLUETOOTH transceiver. This transceiver may allow communication with the nomadic device 103 using a direct signal 119 if, for example, cellular networks are unavailable.

FIGS. 2 a-d show illustrative examples of vehicle-based communication modules that provide communication to a remote network.

FIG. 2 a shows an illustrative example of a communication module 200 combined with a GPS module, wherein a cellular module and GPS are on different boards.

In this illustrative embodiment, a communications module 200 can include a cellular (e.g., and without limitation, GSM or CDMA) antenna 201 that communicates with a remote server over a cellular network. The received cellular signal may be sent from the cellular antenna 201 to a multi-band cellular (e.g., and without limitation, GSM or CDMA) decoder 219 that processes the received signal to produce information usable by the microprocessor 217.

In this illustrative embodiment, the multi-band cellular chip 219, including flash memory 207 and RAM 211, is installed in the module as part of a removable device 223 including a SIM card 221. The SIM card 221 may contain user identifying information that allows access to the cellular network under a particular user's plan.

Additionally, the module includes a GPS chip 203 that can process and decode a signal from the GPS antenna 205 and send this information to a microprocessor 217.

The microprocessor is also in communication with a vehicle data bus that provides access to various vehicle modules, such as RF module 215. Other modules not shown include, but are not limited to, the vehicle cluster, a remote (off-board) GPS system, a radio module, etc. Non-limiting examples of a vehicle data bus include an SAE J1850 bus, a CAN bus, a GMLAN bus, and any other vehicle data buses known in the art. For illustration purposes only, FIGS. 2 a-2 d are represented as using a CAN bus.

FIG. 2 b shows a second exemplary embodiment in which a cellular chip and GPS are on the same board 223. In this illustrative embodiment, the removable board (this board may also be permanently attached to the module) 223 may contain the SIM card 221, a GPS module including a GPS chip 203 and a GPS antenna 205 a, and the Multi-band cellular chip 219 including flash memory 207 and RAM 211.

In another embodiment, the GPS antenna 205 b may be attached to the module separately from this board 223. When a signal comes in from the cellular antenna 201 and/or the GPS antenna 205 b, the signal may be sent to the corresponding cellular/GPS chip 203 for processing, and then passed to the microprocessor 217. The microprocessor 217 interfaces with the CAN transceiver 213 to connect to a vehicle network 214 and vehicle modules such as RF module 215.

FIG. 2 c shows yet another exemplary embodiment in which the cellular module is standalone. In this illustrative embodiment, the GPS module containing the GPS antenna 205 and the GPS chip 203 may connect to the microprocessor 217 through the CAN transceiver 213. Other vehicle modules, such as an RF module 215 can also connect to the microprocessor through the CAN transceiver 213.

In this illustrative embodiment, the removable board 223 may contain a SIM card 221 and a multi-band cellular chip 219, as well as a flash memory 207 and RAM 211. Signals from the cellular antenna 201 may be sent to the board 223 for processing by the multi-band cellular chip 219 before being sent to the microprocessor 217.

FIG. 2 d shows still another exemplary embodiment in which a cellular module is combined with an RF module 215 in the communications module 200. The RF module 215 may continue to talk to the microprocessor 217 through the CAN transceiver 213. In this illustrative embodiment, the GPS module, including the GPS antenna 203 a, 203 b and GPS chip 205 a, 205 b can be located within the communications module 200 or located elsewhere in the vehicle, in which case it may communicate with the microprocessor 217 through the CAN transceiver 213.

Again, in this embodiment, the cellular antenna 201 may send a signal to the multi-band cellular 219, including flash memory 207 and RAM 211. The signal may be processed and sent to the microprocessor 217. The multi band cellular chip 219 may be located on a removable circuit board 223, which may also include a SIM card 221.

FIG. 3 illustrates the operation of a communication module 200 according to one illustrative embodiment. The nomadic device (ND) 103 and/or computer 105 may include software for facilitating the operation of the one or more embodiments. The software may be downloaded to the ND 103 or computer 105 from a website (such as an OEM's website) or, as another example, come factory installed in the ND. In one embodiment, the software may be a programmed in the JAVA language (manufactured and distributed by Sun Microsystems).

In one or more exemplary embodiments, a user may control one vehicle with multiple NDs 103 or computers 105. Additionally or alternatively, the user may use one ND 103 or computer 105 to operate components of multiple vehicles.

The user may activate and operate the software using one or more button or key presses from his or her ND 103 and/or computer 105. In one illustrative embodiment, the ND 103 and/or computer 105 may be equipped with a hot-key from which the software may be activated. Alternatively or additionally, the user may activate and operate the software through a menu selection from a graphical user interface (GUI) displayed on the ND 103 and/or computer 105.

Further, computer readable storage mediums, including, but not limited to, hard disk drives, persistent and non-persistent memory, floppy disks, CDs, DvDs, flash drives, zip drives, etc. may contain instructions that facilitate one or more of the illustrative embodiments. The instructions are typically machine readable and executable by a processor on, for example, without limitation, the nomadic device, the server, and/or the vehicle based microprocessor.

Alternatively or additionally, the user may operate and activate the software through one or more voice-activated commands received by the ND 103 and/or computer 105. The ND 103 and/or computer 105 may include speech recognition software for interpreting and processing commands from a user into machine readable language. In one embodiment, the speech recognition software may be programmed and/or stored to the web server. Non-limiting examples of a user may be a vehicle owner, a vehicle passenger, a vehicle service technician, or a vehicle dealer.

Upon making the request (via, e.g., key button press or voice), one or more data packets may be transmitted from the ND 103 or computer 105 as illustrated in block 300. Non-limiting examples of data (i.e., information) transmitted in the data packets may include a mobile identification number (MIN), a customer identification number, the one or more commands triggered from the ND 103 and/or 105, and the vehicle identification number (VIN). Furthermore, in some embodiments, the one or more data packets transmitted from the ND 103 and/or computer 105 may include instructions for operating according to the one or more requests made by the user.

Referring back to FIG. 3, before or after the data packets are transmitted, a connection may be generated with the server(s) 101 as illustrated in block 302. The server(s) 101 may or may not be a web server. Once a connection to sever(s) 101 is made, the data packets may be received by the server(s) 101 as illustrated in block 304. Alternatively or additionally, a direct connection may be made between the ND 103 or computer 105 and the cellular communication module 200 (i.e., without making a connection to server(s) 101). Accordingly, the operation of one or more embodiments of the present invention may be accomplished without a server.

The server(s) 101 may process one or more received commands for transmission to the vehicle 121. Processing the data packet may include, but is not limited to, authenticating the one or more commands, authenticating the user (e.g., determining if the user is a registered user) and authenticating the cellular/mobile phone (e.g., matching the MIN to the VIN) transmitted in the data packet. In one non-limiting embodiment, the server(s) 101 may process the data packet using one or more look-up tables and validating the information in the data packets against the one or more tables.

The server(s) 101 may be in further communication with one or more databases (not shown). The data may be retrieved from third-party systems, OEM (e.g., vehicle) databases/servers or manually inputted by a user (e.g., an OEM).

In one exemplary embodiment, a determination may be made at the server(s) 101 if the user has any personal preferences as illustrated in block 306. While the preferences may be stored elsewhere, for purposes of illustration, FIG. 3 illustrates the operation based on the personal preferences being stored on the server(s) 101.

The personal preferences may be stored on the server(s) 101. Alternatively or additionally, the personal preferences may be stored in the ND's 103 or computer's 105 memory (not shown). In yet another embodiment, the personal preferences may be stored at the vehicle (e.g., on the SIM card 221, on the microprocessor 217 of the cellular communication module 200, or in a memory module present elsewhere in the vehicle). In this latter embodiment, the server(s) 101 may route the data packets to the vehicle without further processing.

Referring back to FIG. 3, if the user has personal preferences associated with one or more vehicle components, the server(s) 101 may receive instructions to access the stored preferences as illustrated in block 308. In one embodiment, the instructions may be transmitted with the one or more data packets received from the ND 103 and/or computer 105. The server(s) 101 may extract or read these instructions from the data packets to retrieve the stored personal preferences.

In one illustrative embodiment, a further determination may be made at server(s) 101 as to whether a personal identification number (PIN) is required to access the personal preferences or to operate one or more features of the software as illustrated in block 312. The PIN may be stored at server(s) 101 or may be transmitted with the data packets transmitted from the ND 103 and/or the computer 105. If a PIN is required, the server(s) 101 may transmit a request for the PIN as illustrated in block 314. The request may be transmitted to one or more memory locations (e.g., a database) on the server(s) 101 or to the remote terminals 103, 105. The PIN may be retrieved from the server(s) 101 using, for example, a look-up table based on information such as VIN, a customer number, a MIN, or other non-limiting identifiers. It should be understood that the PIN may be retrieved in any other means known in the art and the previous example is illustrative.

For example, it may be desirable to “PIN restrict” only certain features. A tracking feature, for example, may be PIN restricted, since it would allow a person who found a cellular phone to also find the vehicle, and possibly gain entry, depending on the features available on the phone. Accordingly, the tracking feature may require a PIN entry to activate.

In one illustrative embodiment, once a PIN has been entered once, it may not need to be re-entered until the phone has been deactivated and reactivated.

The server(s) 101 may receive the PIN as illustrated in block 316. The PIN may then be validated as illustrated in block 318. If the PIN is not correct, the server(s) 101 may re-transmit the request as represented by loop 320. In one embodiment, a user may reenter a PIN a predetermined number of times (e.g., 3 or 5 times) after entering an incorrect PIN. If the PIN is correct, the server(s) 101 may retrieve the personal preferences associated with the request, as illustrated in block 322, and transmit the one or more data packets with the stored preferences to the cellular communication module as illustrated in block 310.

If a PIN is not required to access the personal preferences or if there are no stored preferences, upon receiving the one or more data packets, the server(s) 101 may transmit the one or more data packets to the cellular communication module as represented in block 310. The one or more data packets may be transmitted over the network (e.g., cellular network 113 or the internet). The cellular communication module 200 may then receive (e.g., via GSM antenna 201) the one or more data packets over the network as represented in block 326. One or more signals for transmission to the vehicle CAN network 214 may then be generated (e.g., by the multi-band GSM decoder 219) as represented in block 328.

In one embodiment, the one or more signals may be decoded and translated for transmission to the CAN interface (e.g., CAN transceiver 213 and vehicle network 214) at the microprocessor 217 which may be in communication with the GSM decoder 219 via electrical communication. (Other vehicle system busses different from the CAN bus may also be communicated with/though) The one or more signals may be decoded for interpretation by the vehicle network 214. The one or more signals (including the data packets) may then be transmitted to the CAN interface (e.g., the CAN transceiver 213) as represented in block 330.

The CAN transceiver 213, upon receiving the one or more request signals, may transmit the one or more request signals to the one or more vehicle components via vehicle network 214.

After one or more operation have been completed based on the request/command by the user, the CAN transceiver 213 may receive the one or more result signals transmitted from the one or more vehicle components as illustrated in block 332. The CAN transceiver 213 may transmit the one or more return signals to the microprocessor 217 for extracting one or more return data packets for transmission to the ND 103 and/or 105 as in block 334. Transmission may be accomplished by the GSM antenna 201 over network 115.

Upon transmitting the one or more result data packets, as illustrated in block 336, the data packets may be transmitted to the remote terminals 103 and/or 105. In one embodiment, the return data packets may be routed through server(s) 101, as illustrated in block 338, which may or may not further process the data packets for transmission to the remote terminals 103 and/or 105. The result data packet(s) may be transmitted to (as illustrated in block 340) and received by the ND 103 and/or computer 105.

A report may be generated and displayed to the user as illustrated in block 342. The report may be generated each time the user requests one or more operations. Alternatively or additionally, the report may be generated at predetermined time intervals or according to a user preference (e.g., on a monthly basis or each time the user specifically requests a report).

In at least one illustrative embodiment, communication between a vehicle based cellular chip and a remote wireless device is possible. This communication can be used, among other things, to send GPS coordinates of a vehicle to the wireless device. The GPS coordinates can be transmitted to a wireless transceiver over a vehicle system bus or through another connection (for example, RF or BLUETOOTH, if the GPS is not connected to a vehicle system bus).

FIG. 4 shows one illustrative embodiment for passively monitoring a vehicle system. In this illustrative embodiment, monitoring is activated 401. Monitoring can be activated from a vehicle computing system, such as the FORD SYNC system. For example, without limitation, a user could select from a touch menu or voice-activate monitoring of a specific vehicle system. Numerous vehicle systems can be passively monitored in this fashion.

In another illustrative embodiment, passive system monitoring can be activated from a remote source, such as a cellular phone or a PC. In this illustrative embodiment, the user may, for example, pull up a menu and choose a system to monitor or systems to monitor. The signal is then sent from the selecting remote device to a server, for example, and the server routes the call to an appropriate vehicle. Verification of the request can be done server side or it can be done at the vehicle itself.

Once the monitoring is activated, a microprocessor included with the vehicle may begin monitoring a selected sensor 403 through, for example, a vehicle system bus. In this illustrative example, a signal can be sent to the sensor or received from the sensor querying a sensor state. The sensor can be a binary sensor (is something in a first state or a second state) or the sensor can be monitoring for a specific threshold change. This monitoring can be done periodically with a power-up strategy or continuously.

Further, in this illustrative embodiment, a power source can be provided to power the microprocessor and/or the sensor itself. Typically, a sensor will require some power, and it may be desirable to use a power source other than the battery. A capacitor can be provided with the vehicle to power the system, or a limited battery charge may be used. In at least one illustrative embodiment the monitoring may be performed, for example, every X minutes so as not to continually drain the power source.

As part of this illustrative process, the system checks periodically to see if the power source is running low 405. If the power source is running low, a low power alert may be sent to a user 407. This alert can be sent, for example, to a remote device such as a cellular phone or a PC. In this illustrative example, the signal is sent from a vehicle microprocessor through a cellular chip to a remote server. The signal is then routed from the remote server to the appropriate remote device, and the user is thus notified of a low power state of the power source.

Once the notification is performed, the system may continue monitoring 403. If monitoring is continued with a low power source, the system may or may not continue to alert the user of the low power state. If the power is not low, or once the low power alert has been sent, the system then checks to see if a change in the state of the sensor has occurred 409. If no change has happened in the sensor state, the system may continue to monitor the sensor 403.

If a change in the sensor state has occurred, then an alert may be sent to the user 411. For example, this alert can be sent to a remote device such as a cellular phone or a PC. This alert can be sent, for example, in the same manner that the low power alert can be sent.

FIG. 5 shows a further illustrative embodiment of a passive monitoring strategy. In this illustrative embodiment, the vehicle system receives a signal 501. This signal can be passed from a remote device, such as a cellular phone or a PC. The signal is routed from the remote device by a server to the vehicle system. The signal may be validated at the server or at the vehicle, for example.

In this illustrative embodiment, once the signal has been received, the system checks the charge of the power source 503 (other than the battery, in this embodiment) that is used to power the microprocessor and/or the sensor.

If the power source is charged 505, the system activates the sensor and/or the monitoring from the microprocessor 515. In this illustrative embodiment, if the secondary power source is not charged 505, the system sends an option to the user to use a battery 507. Thus, in this embodiment, the vehicle battery can be used as an alternative power source to the secondary power source.

The system then receives a response from the user 509 (sent, for example, from a remote device) that instructs the system whether or not the user desires the system to use the battery in place of the secondary power source. If the user does not wish to use the battery 511, the system then exits.

If the user desires to use the battery as a power source, the system activates a battery check option 517. Since the battery is used for vital functions, such as starting a car, in this illustrative embodiment the user is first given an option to use the battery. Even if the user does want to use the battery, the system will monitor the battery in this embodiment to make sure that there is sufficient power remaining in the battery to power the vehicle.

Once the battery check has been initiated, the monitoring system is then activated 515. After the monitoring system has been activated, the vehicle system checks to determine if the battery check is activated 519. If the battery is low, 523, the system terminates the monitoring 525 to preserve battery power. In another illustrative embodiment, the a last check of the monitoring system may be made. In this embodiment, the monitoring is terminated 525 once the battery is determined to be low. Since the user may still believe the sensor is being monitored, the user is notified of the low power state of the battery and the termination of the monitoring 527. If the battery check is not on, or if the battery is not low, the system will continue to monitor the sensor(s) selected by the user for monitoring.

In still another illustrative embodiment, not shown here, the system may also monitor the secondary power source, and then notify the user if that source is running low and provide the option to use the battery 507.

FIG. 6 a shows an illustrative example of monitoring a trailer connection. Similar strategies can be used to monitor a variety of devices. This is but one example of a binary monitoring system where a state is either on or off.

In this illustrative embodiment, the trailer connection monitoring is activated 601. The monitoring system checks to see if the trailer is still attached 603. This can be done by checking a power connection to the trailer, or through the used of a secondary sensor provided for monitoring the connection. If the trailer is still attached, the monitoring continues 601. If the trailer is not connected, the system sends an alert to the user on a remote device 605.

Further, with certain systems, such as trailer monitoring, a secondary action may be performed. In this illustrative embodiment, it may be desirable to activate an alarm system 607. This could, for example, prevent the theft of a trailer while at the same time the user is being notified via a remote device.

In another illustrative example, shown in FIG. 6 b, a sensor having a threshold is monitored. In this example, the device is a rain meter and/or a barometer 611. A rain meter could detect the presence of moisture on a sensor or the windshield, and a barometric pressure change could signal the onset of a storm. Such monitoring might be useful, for example, if a convertible top or a window were down.

In this illustrative embodiment, the system checks one or more sensors to see if a weather change has occurred 613. This could be done through the previously mentioned systems or additional systems. If the weather conditions haven't changed, the system continues to monitor the sensors 611. If the weather conditions change (for example, if a threshold has been crossed on a barometer) an alert is sent to the user via a remote device. The alert can be sent in the manners previously noted.

As with the trailer connection, a secondary action may be taken. In this illustrative embodiment, the secondary action could be to raise the windows of a car or raise the roof of a convertible 617. Or, in the alternative, a user could be provided with the option to have the vehicle system perform one or more of these actions.

FIG. 7 shows an illustrative embodiment of a notification strategy. In at least one illustrative embodiment, it may be desirable to determine if the vehicle is, in fact, occupied before notifying the driver of a change in a condition. For example, if a “lights on” condition were sent to a phone, it may annoy a driver to receive this notification while that driver is still in the vehicle. Accordingly, in this illustrative embodiment, the system checks to see if the vehicle is still occupied before sending a notification.

Numerous possibilities for determining vehicle occupancy exist, and all are suitable for implementation of the illustrative embodiments. For example, a non-exhaustive list includes checking a vehicle power status, checking whether the doors have opened and closed, checking whether an interior camera fails to detect the presence of passengers, checking for no change in position and/or no movement of an accelerometer for a period of time, checking for no voice activity or sounds on an interior microphone.

Some or all of the above examples can be used. Further, a single example might be sufficient to determine occupancy/non-occupancy, or it may be desired to use several of the examples in concert with each other (e.g., without limitation, doors have opened and closed and vehicle power status is “off”).

Numerous passive monitoring strategies can be used and/or combined with the vehicle occupancy detection. For example, a lights and/or door alert may be available. In this illustrative implementation, a vehicle can detect whether lights have been left on and/or one or more doors has been left ajar.

Although not necessary, in this implementation the detection is combined with the vehicle occupancy detection strategy, so that a user is only notified when it is reasonably determined that the vehicle is unoccupied.

Further, for at least some number of these detection strategies, the notification could be performed when, for example, a power down is being performed (so as to use the vehicle's remaining power to run the detection).

In another illustrative example, a lights-on and/or door ajar sensor check is run when a user locks a vehicle using the key fob. This typically indicates that the user is both a) no longer in the vehicle; and b) leaving the vehicle for some period of time.

In yet a further illustrative embodiment, a parking brake monitor is provided as shown in FIGS. 8A-B. This can be especially helpful with manual transmissions, although has equal application to automatic and hybrid transmissions.

In the first illustrative embodiment, shown in FIG. 8 a, the system checks to see if the vehicle has been placed into park, and/or if the vehicle is in neutral and powered down 801. This is not an exhaustive determination of when a parking brake test could be applied, for example, at least one other suitable implementation would be if the vehicle was in neutral and the brake pedal was not depressed. The system then checks to see if the parking brake has been engaged 802.

If the brake is not engaged, then the system checks the GPS coordinates of the vehicle 803 and cross references them with a topographical map 805 or some other map that would indicate an inclined slope.

If the vehicle is on an incline 807, the user is notified 809 that the parking brake is not engaged. FIG. 8 b is similar to the method of FIG. 8 a, except that an incline sensor in the vehicle is used 813 in place of the GPS detection and comparison 803, 805.

Although both of these methods may be combined with vehicle occupancy detection, it may be desirable to forego occupancy detection in these cases, since by the time an occupant, who has left a vehicle in neutral on a slope without the brake engaged, has left the vehicle, it may be too late to stop the vehicle from rolling away.

In still a further illustrative embodiment, a vehicle may transmit the charging/charged status of a battery if it is an electronic vehicle or a hybrid, for example.

Built in vehicle systems could be used for rental car assistance as well, for example. Vehicle locations, rental agreements, payment information, fuel level, etc. could be instantly transmitted to one or more handsets (renter, owner, etc.).

All of the previous examples have generally listed embodiments that are typically performed when a vehicle is turned off or left in a location. But, there are a number of additional possible passive monitoring alerts that can be activated and/or provided when a vehicle is turned on. Generally, in these instances, the sensor(s) can be powered by the vehicle with little concern for the battery expiring from powering the sensor(s).

In a first illustrative embodiment, an example of passive vehicle-on monitoring includes a safety status alert. This can include, but is not limited to, a low battery charge warning, a bulb expired warning, a diagnostic code set warning, a maintenance due warning, a excessive temp (oil, coolant, brake, transmission, etc.) warning, a low oil pressure warning, a low tire pressure (vehicle, trailer) warning, and a parking brake on while driving warning. Certain of these warning, such as parking brake, can be addressed without need to head to a repair station. In other instances, the location or a phone number for the nearest/appropriate repair station can be uploaded to the user's remote device in conjunction with the report.

FIG. 9 shows an example of a safety alert monitoring and transmission system. In this illustrative embodiment, one or more safety sensors are checked by the system 901.

If an alert is needed 903, then the system determines if additional information (such as address, phone number, etc. of service station/dealer/gas station, etc.) is needed 905.

If the additional information is needed, the system looks up the additional information 907 and adds the additional information to the alert message 909. The alert message is then transmitted to the user 911 (the message is also transmitted in the absence of additional information).

A number of active alert thresholds can also be implemented to track driving performance/status of a certain group of drivers or a specific driver.

For example, in at least one illustrative embodiment a valet mode can be set. Similarly, a specific driver mode can be set by, for example, without limitation, use of a certain key to start the car. This may be useful if a teenager or other untrusted driver is driving the car.

When one of these modes is set, the system can send alerts to a user if certain thresholds are passed. These alerts include, but are not limited to, overtemperature monitors, driving with parking brake on monitors, aggressive driving monitors, exiting of certain “geofence” area monitors, excessive speed monitors, airbag deployment or other vehicle safety system activation monitors (in this event, whether or not the vehicle is in a specific user mode, a secondary message may be sent to any and all stored emergency contact information). Additional alerts can include a “sleepy driver” alert, determined by using a Driver Impairment Monitor (DIMON) or other algorithm.

Additionally, a “stranded” alert can be sent if a fuel level is low or zero, tire pressure is low or zero, engine has a shutdown trouble code associated therewith, engine temps are extremely high, etc. and the vehicle is not moving.

Further considerations before sending a stranded alert may include a determination that multiple unsuccessful attempts have been made to start a vehicle. Additionally, the system may check the vehicle GPS coordinates to determine that the vehicle is not at home or in a parking lot, etc.

Seatbelt alerts may also be sent to parents of teen drivers, or even to drivers themselves if a certain distance is traveled without a seatbelt being fastened.

Another example of possible monitoring of an active vehicle could be a highjack alert, wherein a cabin microphone detects the utterance of a certain phrase, and notifies emergency contacts and/or the police that a vehicle occupant may be hijacked. This could be followed up by a responsive notice to the vehicle occupant that a highjacking has been detected and the vehicle is now being tracked using GPS. Of course, it may be desirable not to notify the occupants, so that the kidnappers aren't notified to take evasive action by leaving the vehicle and taking the hostage with them.

In addition to or in alternative, a certain button press combination (of door locks, windows, etc.) could be detected to inform of a hijack situation.

Finally, in still a further illustrative embodiment, a curfew alarm may be provided, that notifies a user if a vehicle is being driven after an established curfew.

Any and all of these monitoring conditions do not necessarily need to be tied to a “valet” or “teen driver” mode, they can all be generally provided for any driver if desired.

FIG. 10 shows an illustrative example of providing monitoring conditions for a specific driver or set of drivers.

In this illustrative embodiment, the system checks to see if a specific driver or a specific driver class is active 1001. As previously mentioned, this could be a “valet” setting, or could be, for example, activation of the vehicle by a certain key given to a specific driver (such as a teenager).

The system then checks to determine if there are any specific alerts associated with that particular driver or driver class 1003. These can include, but are not limited to, the alerts mentioned above.

If there are no specific alerts, the system may exit 1005. If specific alerts are associated, the system monitors one or more sensors associated with those alerts 1007. If an alert condition is present 1009, the system alerts a user 1011 of the existence of the condition. Otherwise, the system returns to monitoring the sensors 1007.

In yet another illustrative embodiment, GPS tracking can be used to determine, for example, a towing instance. If the GPS coordinates of the vehicle change and the vehicle has not been started, then it's likely the vehicle is being towed, and an owner can be alerted. If the customer is notified of the vehicle movement and it is unlikely that a tow event has occurred, the customer could be given the option to notify 911 via the vehicle system as well, and the GPS coordinates of the vehicle could be tracked.

While exemplary embodiments are described above, it is not intended that these embodiments describe all possible forms of the invention. Rather, the words used in the specification are words of description rather than limitation, and it is understood that various changes may be made without departing from the spirit and scope of the invention. Additionally, the features of various implementing embodiments may be combined to form further embodiments of the invention. 

What is claimed is:
 1. A system comprising: a processor configured to: determine that a vehicle has stopped moving; determine that an anomalous vehicle condition exists; determine if vehicle GPS coordinates correspond to a business or other point of interest; and send an alert to a remote party if the vehicle has stopped moving, the anomalous condition exists and the vehicle GPS coordinates do not correspond to a business or other point of interest.
 2. The system of claim 1, wherein the anomalous vehicle condition is a fuel-empty condition.
 3. The system of claim 1, wherein the anomalous vehicle condition is a vehicle over-heated condition.
 4. The system of claim 1, wherein the anomalous vehicle condition is a flat tire condition.
 5. The system of claim 1, wherein the anomalous vehicle condition includes the presence of a diagnostic trouble code generated by the vehicle.
 6. The system of claim 1, wherein the other known location is a vehicle home address.
 7. A computer-implemented method comprising: determining that a vehicle has stopped moving; determining that an anomalous vehicle condition exists; determining if vehicle GPS coordinates correspond to a business or other point of interest; and sending an alert to a remote party if the vehicle has stopped moving, the anomalous condition exists and the vehicle GPS coordinates do not correspond to a business or other point of interest.
 8. The method of claim 7, wherein the anomalous vehicle condition is a fuel-empty condition.
 9. The method of claim 7, wherein the anomalous vehicle condition is a vehicle over-heated condition.
 10. The method of claim 7, wherein the anomalous vehicle condition is a flat tire condition.
 11. The method of claim 7, wherein the anomalous vehicle condition includes the presence of a diagnostic trouble code generated by the vehicle.
 12. The method of claim 7, wherein the other known location is a vehicle home address.
 13. A non-transitory computer readable storage medium, storing instructions that, when executed by a processor, cause the processor to perform a method comprising: determining that a vehicle has stopped moving; determining that an anomalous vehicle condition exists; determining if vehicle GPS coordinates correspond to a business or other point of interest; and sending an alert to a remote party if the vehicle has stopped moving, the anomalous condition exists and the vehicle GPS coordinates do not correspond to a business or other point of interest.
 14. The storage medium of claim 13, wherein the anomalous vehicle condition is a fuel-empty condition.
 15. The storage medium of claim 13, wherein the anomalous vehicle condition is a vehicle over-heated condition.
 16. The storage medium of claim 13, wherein the anomalous vehicle condition is a flat tire condition.
 17. The storage medium of claim 13, wherein the anomalous vehicle condition includes the presence of a diagnostic trouble code generated by the vehicle.
 18. The storage medium of claim 13, wherein the other known location is a vehicle home address. 